Connect to M365
The M365 Settings screen lets you manage your connections to the M365 platform. You most likely provided consents during the Quick Start wizard (Quick Start). Upon consent an Enterprise application is created on your M365 tenant with the required permissions (see table below for details).
Global Admin privileges for the customer Azure tenant are required to provide consents.
The table below describes the required consents and the Enterprise applications that are created on your M365 tenant.
Consent |
Description |
|||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
M365 Login |
Provide the application permissions to authenticate users with your M365 tenant credentials. The application reroutes users to M365 for authentication (Azure Active Directory authentication-Microsoft OpenID Connect-Oauth 2). The permissions are required for the SmarTAP application to authenticate users utilizing your tenant AAD authentication, and Microsoft Open ID Connect (Oauth 2) authentication. The permissions enable Live Platform to reroute users accessing the Live Platform application either from a browser or from the Live Platform Teams application (see row below) to be authenticated according to your organizational M365 policy. The Deployment generates the Enterprise application <LivePlatformSer verName>-auth.
|
|||||||||||||||
Publish Teams Client App in your Teams Store |
Add the application to users Teams Clients for access of the application within Microsoft Teams. Click the publish button to access the app within your Teams store using M365 Administrator permissions. In the store, you can set policies for installing and automatically pinning the application for specific groups are users. This consent is part of the M365 Login application (shown above). In addition to the permissions shown above, the following are added:
Publishing the app makes it available for users in the tenant organization within Teams store. Each user needs to add the application from their Teams admin center in order to access it from Teams. |
|||||||||||||||
Read Azure Active Directory Users and Groups |
Provide the application permissions to read AAD groups and users from your M365 tenant to enable the groups' targeted users for recording and access to the application. Deployment of Live Platform generates the Enterprise application <LivePlatformServerName>-aad.
|
|||||||||||||||
Recording Calls (Teams Bot consent to join calls) |
Provide the application's Teams Bot with permissions to join your Tenant's Teams calls to record the calls' info and media. The calls-app permissions are required for the Live Platform Bot application to join your Teams’ tenant calls and to receive the media to be recorded. Deployment of Live Platform generates the Enterprise application <LivePlatformServerName>-hue.
|
|||||||||||||||
Redundant Recording Calls (Second Teams Bot consent to join calls) |
Provide the application's Redundant Teams Bot with permissions to join your tenant's Teams calls to record the calls' info and media. The calls-app permissions are required for the Live Platform Bot application to join your Teams’ tenant calls and to receive the media to be recorded. Deployment of Live Platform generates the Enterprise application <LivePlatformServerName>-hue-paired.
This consent is required in the event where a Pro User license has been configured for the service. |
➢ | Do the following: |
1. | In the Icon pane, click ![]() |
2. | Click the Grant Admin Consent button adjacent to each Consent for which you wish to activate. A green tick is displayed once the consent process has completed successfully. |